Our user is using the grid (our first implimentation of it) and using the default image editor. He's uploading an image 3350 px wide(huge) and selecting it. I can use the ?width=265 querystring in the .cshtml to size it down, but my fearless leader is concerned about the server time to resize the image(s). My fearless leader wants us to control the upload size by giving options or by hardcoding 4 different upload sizes and selecting the most appropriate one in the code on rendering the page. I have many questions....Does the ?width=365 cause a server load time delay that is worth worrying about? Is there a way to create maybe 3 or 4 specific upload sizes? How has anyone else tackled this issue.
Fear not! Using the querystring width variable is using ImageProcessor and the resized image is cached to disk on the first request, so there is no advantage to uploading multiple images at all.
[EASY] Rendering Images with optimal load times
Our user is using the grid (our first implimentation of it) and using the default image editor. He's uploading an image 3350 px wide(huge) and selecting it. I can use the ?width=265 querystring in the .cshtml to size it down, but my fearless leader is concerned about the server time to resize the image(s). My fearless leader wants us to control the upload size by giving options or by hardcoding 4 different upload sizes and selecting the most appropriate one in the code on rendering the page. I have many questions....Does the ?width=365 cause a server load time delay that is worth worrying about? Is there a way to create maybe 3 or 4 specific upload sizes? How has anyone else tackled this issue.
Hi Doug,
Fear not! Using the querystring width variable is using ImageProcessor and the resized image is cached to disk on the first request, so there is no advantage to uploading multiple images at all.
Jeavon
Thank you Jeavon for the quick answer!
is working on a reply...